<!-- wp:cover-image {"url":"https://testgutenberg.com/wp-content/uploads/2017/12/testimage.jpg","align":"full","id":401} -->
<div class="wp-block-cover-image has-background-dim alignfull" style="background-image:url(https://testgutenberg.com/wp-content/uploads/2017/12/testimage.jpg)">
    <p class="wp-block-cover-image-text">Even cover images are easy</p>
</div>
<!-- /wp:cover-image -->

<!-- wp:subhead -->
<p class="wp-block-subhead"><em>﻿Howdy! This is Frontenberg, a frontend instance of Gutenberg with some restrictions so that anyone can test and explore.</p>
    <!-- /wp:subhead -->

<!-- wp:paragraph {"dropCap":true} -->
<p class="has-drop-cap">In 2018, WordPress will modernize, streamline, and simplify the content creation experience with Gutenberg. It optimizes for direct manipulation of the visual presentation of the content, instead of through indirect means, like metaboxes. The new editor offers content creators a straightforward way to find, insert, and work with elements on the page. We think this experience is so compelling that editorial teams will quickly want to adopt it into their workflow.</p>
<!-- /wp:paragraph -->

<!-- wp:image {"align":"right","width":312,"height":234} -->
<figure class="wp-block-image alignright"><img src="https://wordpress.org/gutenberg/files/2017/12/Dropcap.png" alt="" width="312" height="234" /></figure>
<!-- /wp:image -->

<!-- wp:paragraph -->
<p>As exciting as it is, it also represents the biggest change to the WordPress user experience in several years. We know very well that many folks have extensive integrations with the current WordPress editor and will want a gradual transition. Upfront planning will be required for a smooth transition to Gutenberg. We are here to help answer any questions on preparing development and editorial teams for the transition.</p>
<!-- /wp:paragraph -->

<!-- wp:quote -->
<blockquote class="wp-block-quote">
    <p><em>As many of you know, backward compatibility is a core principle of WordPress, and it is no different with Gutenberg.</em></p>
</blockquote>
<!-- /wp:quote -->

<!-- wp:paragraph -->
<p>Would your preference be to opt-in to the new editor gradually over time? In order to preserve publishing continuity, there is a plugin called <a href="https://wordpress.org/plugins/classic-editor/">Classic Editor</a> that will allow everyone to use the current editor as they work on transition plans.</p>
<!-- /wp:paragraph -->

<!-- wp:quote {"style":2} -->
<blockquote class="wp-block-quote is-large">
    <p>Take comfort in the fact that you 'can' keep your current publishing flow... and then take some time to explore the possibilities that Gutenberg opens up to you.</p><cite>By M</cite>
</blockquote>
<!-- /wp:quote -->

<!-- wp:image -->
<figure class="wp-block-image"><img src="https://wordpress.org/gutenberg/files/2017/12/Gutenberg.png" alt="" /></figure>
<!-- /wp:image -->

<!-- wp:paragraph -->
<p>The current WordPress editor is an open text window—it’s always been a wonderful blank canvas for writing, but when it comes to building posts and pages with images, multimedia, embedded content from social media, polls, and other elements, it required a mix of different approaches that were not always intuitive:</p>
<!-- /wp:paragraph -->

<!-- wp:list -->
<ul>
    <li>Media library/HTML for images, multimedia and approved files.</li>
    <li>Pasted links for embeds.</li>
    <li>Shortcodes for specialized assets from plugins.</li>
    <li>Featured images for the image at the top of a post or page.</li>
    <li>Excerpts for subheads.</li>
    <li>Widgets for content on the side of a page.</li>
</ul>
<!-- /wp:list -->

<!-- wp:paragraph -->
<p>We're excited to see what innovative uses our clients come up with!</p>
<!-- /wp:paragraph -->

<!-- wp:gallery {"align":"full"} -->
<ul class="wp-block-gallery alignfull columns-3 is-cropped">
    <li class="blocks-gallery-item">
        <figure><img src="https://testgutenberg.com/wp-content/uploads/2018/02/abril-case-study.jpg" alt="" data-id="757" /></figure>
    </li>
    <li class="blocks-gallery-item">
        <figure><img src="https://testgutenberg.com/wp-content/uploads/2018/02/facebook.jpg" alt="" data-id="760" /></figure>
    </li>
    <li class="blocks-gallery-item">
        <figure><img src="https://testgutenberg.com/wp-content/uploads/2018/02/usp-case-study1.jpg" alt="" data-id="761" /></figure>
    </li>
    <li class="blocks-gallery-item">
        <figure><img src="https://testgutenberg.com/wp-content/uploads/2018/02/variety_magazine_native-1-full.jpg" alt="" data-id="762" /></figure>
    </li>
</ul>
<!-- /wp:gallery -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:heading {"align":"center"} -->
<h2 style="text-align:center">Get involved</h2>
<!-- /wp:heading -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:paragraph -->
<p>Rather than wait to see what happens, help shape the direction and success of Gutenberg. The best-prepared sites won’t be the ones following the chatter, they’ll be <em>part</em> of that chatter. It’s worth joining the WordPress.org slack (<a href="https://href.li/?https://make.wordpress.org/chat/">https://make.wordpress.org/chat</a>) and checking out the #core-editor channel. If you have questions, you can ask for help in there.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>The most targeted way to help the people building this new user experience is to test the editor using a particular script and set of tasks. You can <a href="https://make.wordpress.org/test/handbook/call-for-testing/gutenberg-testing/">find the tests and instructions right here</a>.</p>
<!-- /wp:paragraph -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:heading {"align":"center"} -->
<h2 style="text-align:center">Resources</h2>
<!-- /wp:heading -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:text-columns -->
<div class="wp-block-text-columns alignundefined columns-2">
    <div class="wp-block-column">
        <p><strong>For product owners / editors<br/>- <a href="https://wordpress.org/gutenberg/handbook">Gutenberg handbook</a><a href="https://wordpress.org/gutenberg/handbook/outreach/articles/"><br/></a>- <a href="http://gutenberg.news/">Gutenberg news<br/></a>- <a href="https://vip.wordpress.com/2017/12/06/gutenberg/">Gutenberg for VIPs<br/></a>- <a href="https://hmn.md/white-papers/gutenberg-the-new-wordpress-editor/">Human Made’s white paper<br/></a>- <a href="https://twitter.com/gutenbergtimes">Gutenberg news</a> (Twitter)</strong></p>
    </div>
    <div class="wp-block-column">
        <p><strong>For developers<br/></strong>- <a href="https://riad.blog/2017/10/16/one-thousand-and-one-way-to-extend-gutenberg-today/">Extending Gutenberg today</a><strong><br/></strong>- <a href="https://riad.blog/2017/12/11/with-gutenberg-what-happens-to-my-custom-fields/">What happens to my custom meta fields</a>?<strong><br/></strong>- ﻿<a href="https://github.com/wp-cli/scaffold-command#wp-scaffold-block">wp-cli command for static block</a><strong><br/></strong>- <a href="https://github.com/ahmadawais/Gutenberg-Boilerplate">Gutenberg boilerplate﻿</a></p>
    </div>
</div>
<!-- /wp:text-columns -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:heading {"align":"center"} -->
<h2 style="text-align:center">The WordPress of tomorrow</h2>
<!-- /wp:heading -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:video -->
<figure class="wp-block-video"><video controls src="https://videos.files.wordpress.com/AvC6H2JI/video-de223da1f6.mp4"></video></figure>
<!-- /wp:video -->

<!-- wp:separator -->
<hr class="wp-block-separator" />
<!-- /wp:separator -->

<!-- wp:latest-posts /-->
